The APN Profile configuration mode defines a set of parameters controlling the SGSN or MME behavior when a specific APN is received or no APN is received in a Request. An APN profile is a key element in the Operator Policy feature and an APN profile is not used or valid unless it is associated with an APN and this association is specified in an operator policy (see the Operator Policy Configuration Mode Commands chapter elsewhere in the Command Line Interface Reference).
The SGSN and the MME each support a total of 1000 APN profile configurations per SGSN/MME and up to 50 APN profiles can be associated with a single operator policy. For additional SGSN limit information, refer to the Engineering Rules appendix in the SGSN Administration Guides.
[local]asr5000(apn-profile-<profile_name>)#
Resets the configuration to the default value; i.e. fallback-for-dns.
This keyword instructs the system to only use locally configured addresses and not to use DNS query.
The following command sets the address resolution mode to use local addresses only if the DNS query fails:
cc { local-value-for-scdrs behavior bit_value profile index_bit | prefer { hlr-value-for-scdrs | local-value-for-scdrs } }
If the HLR provides the charging characteristics with behavior bits and profile index and the operator wants to ignore what the HLR provides, then specify the prefer local-value-for-scdrs keyword with this command.
bit_value: Must be a hexadecimal value between 0x0 and 0xFFF.
index_bit: Must be an integer from 1 to 15.
|
•
|
1 for hot billing
|
|
•
|
2 for flat billing
|
|
•
|
4 for prepaid billing
|
|
•
|
8 for normal billing
|
|
•
|
hlr-value-for-scdrs: Instructs the system to use charging characteristic settings received from the HLR for S-CDRs.
|
|
•
|
local-value-for-scdrs: Instructs the profile preference to only use locally configured/stored charging characteristic settings for S-CDRs.
|
Default: hlr-value-for-scdrs
description description
Indicate that APN profile apnprof1 is to be used for customers in Saudi Arabia and that the profile was created on April 10th of 2010:
description “apnprof1 defines APNs for customers in Saudi Arabia (4/10/10).”
The following command instructs the SGSN not to permit establishment of a direct tunnel with a GGSN:
dns-extn { charg-id { binary | decimal | hexadecimal } | lac-rac | msisdn start-offset start_digits end-offset end-digits | rnc-id [ charg-id { binary | decimal | hexadecimal } ] }
msisdn start-offset start_digits
start_digits: An integer from 1 to 14 that identifies the position of the first digit in the MSISDN to start the offset.
end-offset end-digits
end-digits: An integer from 2 to 15 that identifies the position of the last digit in the MSISDN to be part of the offset.
|
•
|
In addition, it is necessary to configure appropriate DNS entries to enforce the selection of the required GGSN. After appending the MSISDN digits to the DNS query string, the string will have the form: ni.<digits>.mnc*.mcc*.gprs. After appending the LAC/RAC information to the DNS query string, the string will have the form: <apn_network_id>.racAAAA.lacBBBB.<apn_operator_id> , where the AAAA and BBBB are Hex-coded digits (less than 4 significant digits and one or more zero (“0”) digits will be inserted to the left side of the Hex to fill the 4-digit coding).
After appending the charging characteristic (SCHAR) information, the DNS string will take the following form: <apn_network_id>.<profile_index>.<apn_operator_id>. The profile index in the following example has a value 10: quicknet.com.uk.1010.mnc234.mcc027.gprs.
If the RNC-ID information is configured to be a part of the APN name, and if inclusion of the profile index of the charging characteristics information is also enabled before the DNS query is sent, then the profile index is included after the included RNC-ID and the DNS APN name will appear in the following form: <apn_network_id>.<rnc_id>.<profile_index>.<apn_operator_id>.
The resulting APN DNS query string would have appended 7 digits (2233445)to the APN NI so that it would appear something like wap98.testnetz.ca.2233445.MNC009.MCC262.GPRS
In the following example, the DNS query for a subscriber using RNC 0321 with the profile index of value 8 would appear as: quicknet.com.uk.0321.1000.mnc234.mcc027.gprs.
no gateway-address ip_address
priority priority
priority : Enter an integer from 1 to 100 to assign a priority to the GGSN IP address. Note that the lower the integer is actually the higher the priority, so that 1 is the highest priority.
weight : Enter an integer from 1 to 100 to give a weight to the GGSN identified.
Also use this command to setup GGSN pools - primary and secondary pools with up to 16 GGSNs in each pool. By default, GGSNs will always be selected from the primary pool. However, working in tandem with the ggsn-fail-retry-timer command configuration (SGTP service configuration mode) which enables the local DNS feature, some of the primary GGSNs can be temporarily blacklisted if they become unavailable or overburdened.
This keyword is required as part of the gtp command to instruct the SGSN to set a proprietary GTPC private extension (in the LORC Intimation IEs) in the event of loss of radio coverage (LORC). These private extensions are only understood by a GGSN with an Overcharging Protection license.
This keyword set is required as part of the gtp command to instruct the SGSN to forward the private extension ‘flag’ to the GGSN in the event of a loss of radio coverage (LORC).
This optional keyword instructs the SGSN to also forward the LORC private extension to the peer SGSN.
gtp private-extension is one of the two commands required to enable the Overcharging Protection feature. The second command sets the RANAP cause code in the Iu Release to enable the SGSN to detect the LORC state of the MS/UE. This second command is configured in the IuPS service and is explained in the IuPS Service Configuration Mode chapter.
When there is a loss of coverage and the Overcharging Protection feature is enabled with the gtp private-extension command, then the SGSN includes the proprietary private extension in the GTP LORC Intimation IE messages. This LORC IE is also included in UPCQ, DPCQ, and SGSN Context Response GTP messages.
Refer to the SGSN Overview chapter of the SGSN Administration Guide for functional information regarding the Overcharging Protection feature.
ipv4: Specifies that an IPv4 ACL is being added to the access group.
ipv6: Specifies that an IPv6 ACL is being added to the access group.
access-group acl_name
Specifies the name of the ACL being added to the access group. acl_name must be an existing IPv4 or IPv6 ACL name and be from 1 to 47 alpha and/or numeric characters.
IPv4 ACLs are configured through the Context Configuration Mode using the ip access-list command.
IPv6 ACLs are configured through the Context Configuration Mode using the ipv6 access-list command.
The following command configures the APN profile to use an IPv4 ACL named acl-3-permit to apply rules to downlink data sent to UEs that are currently in idle mode:
idle-mode-acl ipv4 access-group acl-3-permit
ip { qos-dscp { { downlink | uplink } { background forwarding | conversational forwarding | interactive traffic-handling-priority priority forwarding | streaming forwarding } + } | source-violation { deactivate [ all-pdp | exclude-from accounting | linked-pdp | tolerance-limit } | discard [ exclude-from-accounting ] | ignore }
Important: All parameters not specifically configured will be included in the configuration with default values.Configures the packets for either downlink or uplink direction. downlink and uplink configuration must include one or more of the following:
|
•
|
background - Configures the DSCP marking to be used for packets of sessions subscribed to 3GPP background class. Must be followed by a DSCP marking
|
|
•
|
conversational - Configures the DSCP marking to be used for packets of sessions subscribed to 3GPP conversational class. Must be followed by a DSCP marking
|
|
•
|
interactive - Configures the DSCP marking to be used for packets of sessions subscribed to different traffic priorities in the 3GPP interactive class. Must be followed by a traffic handling priority (THP): 1, 2, or 3.
|
|
•
|
streaming - Configures the DSCP marking to be used for packets of sessions subscribed to 3GPP streaming class. Must be followed by a DSCP marking
|
|
•
|
deactivate - deactivate the PDP context with one of the following conditions:
|
|
•
|
all-pdp - deactivates all PDP context of the MS/UE. Default is to deactivate errant PDP contexts.
|
|
•
|
exclude-from-accounting - excludes packets having an invalid source IP address from the statistics used in the accounting records.
|
|
•
|
linked-pdp - deactivate all associated pdp contexts (primary and secondary). Default is to deactivate errant pdp context.
|
|
•
|
tolerance-limit - Configures maximum number of allowed IP source violations before the session is deactivated.
|
|
•
|
discard - discard errant packets, can include the following option:
|
|
•
|
exclude-from-accounting - excludes packets having an invalid source IP address from the statistics used in the accounting records.
|
|
•
|
ignore - ignore checking of packets for MS/UE IP source violation.
|
|
•
|
deactivate - defines which PDP context should be deactivated:
|
|
•
|
all-pdp - deactivates all PDP contexts.
|
|
•
|
linked-pdp - deactivates only linked PDP contexts.
|
|
•
|
detach-when - defines the condition that warrants a detach:
|
|
•
|
all-pdp-inactive - detach when all PDP contexts are inactive.
|
|
•
|
any-pdp-inactive - detach when any PDP context is inactive.
|
timeout minutes minutes
minutes: Must be an integer from 1 to 1440. Note that even though the timeout is set for minutes, the configuration displays in seconds.
no pgw-address ip_address
weight weight
weight: Enter an integer from 1 to 100 to give a weight to the P-GW IP address.
pgw-address 1.2.3.4
max-ul mbr-up
mbr-up : Enter a value from 0 to 1410065408.
max-dl mbr-dwn
mbr-dwn : Enter a value from 0 to 1410065408.
Important: To enable any of the values/features configured with this command, the qos prefer-as-cap configuration (also in the APN profile configuration mode) must be set to either local or both-hlr-and-local. |
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
all-values - This option will change the configuration to predefined values for all the relevant QoS parameters for the class. This keyword is not used if other options are to be defined. The predefined values are:
|
|
•
|
arp - Sets the allocation/retention priority. Enter an integer from 1 to 3.
|
|
•
|
gbr-down - Guaranteed Kbps rate for the downlink direction. Enter an integer from the range 1 to 256000.
|
|
•
|
gbr-up - Guaranteed Kbps rate for the uplink direction.. Enter an integer from 1 to 256000.
|
|
•
|
mbr-down - Maximum Kbps rate for the downlink direction. Enter an integer from the range 1 to 256000.
|
|
•
|
mbr-map-down from from_kbps to to_kbps - Map received HLR MBR (from value) to a locally configured downlink MBR value (to value) :
|
|
•
|
from_kbps - Enter an integer from 1 to 25600.
|
|
•
|
to_kbps - Enter an integer from 1 to 25600.
|
|
•
|
mbr-map-up from from_kbps to to_kbps - Map received HLR MBR (from value) to a locally configured uplink MBR value (to value) :
|
|
•
|
from_kbps - Enter an integer from 1 to 25600.
|
|
•
|
to_kbps - Enter an integer from 1 to 25600.
|
|
•
|
mbr-up - Maximum Kbps rate for the uplink direction. Enter an integer from 1 to 256000.
|
|
•
|
min-transfer-delay - Minimum transfer delay in milliseconds. Enter an integer from 80 to 4000.
|
|
•
|
4: represents 4*10^-3
|
|
•
|
7: represents 10^-5
|
|
•
|
9: represents 6*10^-8
|
|
•
|
1: represents 5*10^-2
|
|
•
|
2: represents 10^-2
|
|
•
|
3: represents 5*10^-3
|
|
•
|
5: represents 10^-3
|
|
•
|
6: represents 10^-4
|
|
•
|
7: represents 10^-5
|
|
•
|
8: represents 10^-6
|
|
•
|
4: represents 4*10^-3
|
|
•
|
7 : represents 10^-5
|
|
•
|
9: represents 6*10^-8
|
|
•
|
1: represents 5*10-2
|
|
•
|
2: represents 10^-2
|
|
•
|
3: represents 5*10^-3
|
|
•
|
5: represents 10^-3
|
|
•
|
6: represents 10^-4
|
|
•
|
7: represents 10^-5
|
|
•
|
8: represents 10^-6
|
|
•
|
sdu - Signalling data unit keyword, must include one of the following options:
|
|
•
|
delivery-order- Enter one of the two following options:
|
|
•
|
no- Without delivery order
|
|
•
|
yes- With delivery order
|
|
•
|
erroneous- Enter one of the two following options:
|
|
•
|
no- Erroneous SDUs will not be delivered
|
|
•
|
no-detect- Erroneous SDUs are not detected (‘-’)
|
|
•
|
yes- Erroneous SDUs will be delivered
|
|
•
|
error-ratio- The SDU error-ratio range is from 10^-3 to 10^-6. Enter an integer from 1 to 6, where:
|
|
•
|
3- Represents 10^-3
|
|
•
|
4- Represents 10^-4
|
|
•
|
6- Represents 10^-6
|
|
•
|
max-size- Defines the maximum number of octets (size) of the SDU. Enter an integer from 10 to 1502.
|
|
•
|
thp - Sets the traffic handling priority. Enter an integer from 1 to 3.
|
Important: Typically this command is only used to define QoS parameters when the APN record does not exist in the subscription record. Repeat the command as often as needed with different options to define all required QoS criteria. For example, to configure the maximum bit rate (MBR) for the downlink and uplink directions for a traffic class, this command must be used twice, specifying mbr-down once and mbr-up once.
Advantage for local mapping of MBR: some HLRs cannot be configured with high MBR values. Using the mbr-map-up and the mbr-map-down parameters allows the SGSN to be configured to treat a specific HLR value as meaning the desired high MBR value. In a case where the HLR does not support HSPA+ bit rates, but the handsets and network do, this feature allows the operator to overcome limitations on the HLR and provide HSPA+ bit rates by overwriting the provisioned HLR-QoS MBR values with SGSN-configured values. When MBR mapping is configured, if QoS is preferred as the HLR value, then the subscription QoS MBR received from the HLR is compared with the "from" value in the table. If it matches, then it is converted to the value specified by the "to" value in the table. QoS negotiation happens based on the converted value.
qos class conversational all-values
max-ul mbr-up
mbr-up: Enter a value from 0 to 1410065408.
max-dl mbr-up
mbr-up: Enter a value from 0 to 1410065408.
qos default-bearer { arp arp_value [ preemption-capability { may | shall-not } | vulnerability { not-preemptable | preemptable } ] | qci qci }
arp arp_value
arp_value: Enter a value from 1 to 15.
|
•
|
may: Bearer may be preempted
|
|
•
|
shall-not: Bearer shall not be preempted
|
|
•
|
not-preemptable: Bearer cannot be preempted.
|
|
•
|
preemptable: Bearer can be preempted.
|
qci qci
Specifies the QoS Class Identifier for the default bearer profile. qci must be an integer value from 0 to 255.
Important: Command and keyword names have changed. prefer has become prefer-as-cap and hlr has become hlr-subscription. These changes will not impact configuration generated with earlier releases as the keywords are aliases for the previous names.This keyword instructs the SGSN to use, as the capping value during session establishment, the lower of either the locally configured QoS bit rate or the HLR subscription.
Important: This command should be used in conjunction with the max-contexts command to limit the maximum possible bandwidth consumption by the APN.qos rate-limit direction { downlink | uplink } [ burst-size [ auto-readjust | bytes ] | class { background | conversational | interactive traffic_priority | streaming } | exceed-action { drop | lower-ip-precedence | transmit } violate-action { drop | lower-ip-precedence | transmit } ] +
remove qos rate-limit direction { downlink | uplink } [ class { background | conversational | interactive traffic_priority | streaming } ]
Important: If no APN profile is configured, the QoS default behavior is to use the information provided by the SGSN. downlink - This is the direction from GGSN to MS. (from Gn to Iu/Gb).
uplink - This is the direction from MS to GGSN (from Iu/Gb to Gn).
|
•
|
bytes : Must be an integer from 1 through 6000000.
|
Important: It is recommended that the minimum value of this parameter be configured to the greater of the following two values: (1) 3 times greater than packet MTU for the subscriber connection, or (2) 3 seconds worth of token accumulation within the “bucket” for the configured peak-data-rate. In addition, if the committed-data-rate parameter is specified, the burst-size is applied to both the committed and peak rates.|
•
|
auto-readjust : This keyword enables dynamic burst-size calculation, for traffic policing, at the time PDP Activation/Modification is negotiated using QoS maximum bit-rates and guaranteed bit-rates.
|
|
•
|
duration seconds : Must be an integer from 1 to 30. This keyword sets the number of seconds that the dynamic burst-size calculation will last. This allows the traffic to be throttled at the negotiated rates.
|
|
•
|
background : Specifies the QOS for traffic patterns in which the data transfer is not time-critical (for example email exchange). This traffic pattern should be the lowest QOS.
|
|
•
|
conversational : Specifies the QOS for traffic patterns in which there is an constant flow of packets in each direction, upstream and downstream. This traffic pattern should be the highest QOS.
|
|
•
|
interactive traffic_priority : Specifies the QOS for traffic patterns in which there is an intermittent flow of packets in each direction, upstream and downstream. This traffic pattern should be a higher QOS than the background pattern, but not as high as that for the streaming pattern. traffic_priority is the 3GPP traffic handling priority and can be an integer 1,2 or 3.
|
|
•
|
streaming : Specifies the QOS for traffic patterns in which there is a constant flow of data in one direction, either upstream or downstream. This traffic pattern should be a higher QOS than the interactive pattern, but not as high as that for the conversational pattern.
|
Important: If this keyword is omitted, the same values are used for all classes.|
•
|
drop: Drop the packet
|
|
•
|
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
|
|
•
|
transmit: Transmit the packet
|
|
•
|
drop : Drop the packet
|
|
•
|
lower-ip-precedence : Transmit the packet after lowering the IP precedence
|
|
•
|
transmit : Transmit the packet
|
Important: If either exceed action or violate action is set to “lower-ip-precedence”, this command may override the configuration of the ip qos-dscp command in the GGSN service configuration mode for packets from the GGSN to the SGSN. In addition, the GGSN service ip qos-dscp command configuration can override this APN setting for packets from the GGSN to the Internet.
Important: If a subscribed traffic class is received, the system changes the class to background and sets the following parameters: The uplink and downlink guaranteed data rates are set to 0. If the received uplink or downlink data rates are 0 and traffic policing is disabled, the default of 64 kbps is used. When enabled, the APN configured values are used. If the configured value for downlink max data rate is larger than can fit in an R4 QoS profile, the default of 64 kbps is used. If either the received uplink or downlink max data rates is non-zero, traffic policing is employed if enabled for the “Background” class. The received values are used for responses when traffic policing is disabled.ranap allocation-retention-priority-ie subscription-priority priority class { { background | conversational | interactive | streaming } { not-pre-emptable | priority | queuing-not-allowed | shall-not-trigger-pre-emptable } + }
Important: All parameters not specifically configured will be included in the configuration with default values.[ default | remove | no ] ranap allocation-retention-priority-ie [ subscription-priority priority class { background | conversational | interactive | streaming } ]
subscription-priority priority
priority must be an integer from 1 to 3.
|
•
|
background - background class of service
|
|
•
|
conversational - conversational class of service
|
|
•
|
interactive - interactive class of service
|
|
•
|
streaming - streaming class of service
|
|
•
|
priority - smallest number is the highest priority. Value must be an integer from 1 to 15
|
This command can be used multiple times to define multiple priorities, with different combinations of subscription-priority and class.
ranap allocation-retention-priority-ie subscription-priority 0 priority class conversational not-pre-emptable priority 1 shall-not-trigger-pre-emptable
ranap allocation-retention-priority-ie subscription-priority 1 priority class conversational not-pre-emptable priority 4 shall-not-trigger-pre-emptable
ranap allocation-retention-priority-ie subscription-priority 2 priority class conversational not-pre-emptable priority 7 shall-not-trigger-pre-emptable
ranap allocation-retention-priority-ie subscription-priority 3 priority class conversational not-pre-emptable priority 10 shall-not-trigger-pre-emptable
restrict access-type { { gprs | umts } [ qos-class { background | conversational | interactive | streaming } ] }
|
•
|
background - Specifies the QoS class as background service session
|
|
•
|
conversational - Specifies the QoS class as conversational service session
|
|
•
|
interactive - Specifies the QoS class as interactive service session
|
|
•
|
streaming - Specifies the QoS class as streaming service session
|
